home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Columbia Kermit
/
kermit.zip
/
newsgroups
/
misc.19981211-19990422
/
000225_news@watsun.cc.columbia.edu _Mon Feb 15 21:26:19 1999.msg
< prev
next >
Wrap
Internet Message Format
|
2020-01-01
|
2KB
Return-Path: <news@watsun.cc.columbia.edu>
Received: from newsmaster.cc.columbia.edu (newsmaster.cc.columbia.edu [128.59.59.30])
by watsun.cc.columbia.edu (8.8.5/8.8.5) with ESMTP id VAA04068
for <kermit.misc@watsun.cc.columbia.edu>; Mon, 15 Feb 1999 21:26:18 -0500 (EST)
Received: (from news@localhost)
by newsmaster.cc.columbia.edu (8.8.5/8.8.5) id VAA29642
for kermit.misc@watsun.cc.columbia.edu; Mon, 15 Feb 1999 21:14:12 -0500 (EST)
X-Authentication-Warning: newsmaster.cc.columbia.edu: news set sender to <news> using -f
From: dold@92.usenet.us.com
Subject: Re: Scripting F1, Downarr
Date: 16 Feb 1999 02:13:56 GMT
Organization: a2i network
Message-ID: <7aak94$b7j$1@samba.rahul.net>
To: kermit.misc@mailrelay2.cc.columbia.edu
Jeffrey Altman (jaltman@watsun.cc.columbia.edu) wrote:
: Correct. Althought, ESC O P is not F1, it is PF1. A VT100 unlike a
: VT520 does not have a F1 key.
That's what got me back on the right track.
It's been so long since I played with the keymaps.
I've gleaned the key sequence desired from a combination of infocmp -1
on the target unix platform, and capturing keystrokes from a
VT-whatever-it-is terminal that the system seems to like.
Now I'm stuck in a different place. I can feed it appropriate
down-arrows, and F1 keys to get through the menu, but the program
itself seems to want a real terminal. If I take the .ksc up to the
point where the program should be running, I can see that it is there
(ps -f on Unix), but occupying no CPU time. If I "connect" from the
script at this point, the output that I was expecting comes onto the
screen, and it starts using CPU time.
I really don't care about the output. I can check externally to see if
the function completed successfully. In fact, in this one case, I'm
only doing it because the program runs for over an hour, and I don't
want to wait for it to finish ;-) If I'm at work, I just fire it off
on an unused terminal, but from home, I can't quite get that to fly in
the background.
I tried "log debug", but that gives me too much info... I can't tell
what I might need to do to make it run.
--
---
Clarence A Dold - dold@network.rahul.net
- Pope Valley & Napa CA.